Communication across one or more enterprise boundaries regarding the occurrence of a workflow event

ABSTRACT

A computer implemented method for workflow communication is provided. The method includes the following steps. First, one or more workflows are executed. Then an event manger is triggered on the occurrence of a predefined event on the workflow. Finally, a message based on the event is formulated and sent to a fixed group.

RELATED APPLICATIONS

This application is a continuation-in-part of U.S. patent Ser. No.09/092,348, filed Jun. 5, 1998, now issued U.S. Pat. No. 6,119,149 onSep. 12, 2000. This application is related to U.S. Pat. No. 6,289,385B1,entitled “System and Method for Creating an Object Workspace,” U.S. Pat.No. 6,334,146, entitled “System And Method For Remotely Accessing Data,”U.S. patent application Ser. No. 09/156,334, entitled “Method and Systemfor Managing Collaboration Within and Between Enterprises,” U.S. patentapplication Ser. No. 09/156,333, entitled “Workflow Synchronization,”U.S. Pat. No. 6,289,384B1, entitled “System and Method for EventNotification Through a Firewall,” U.S. patent application Ser. No.09/154,661, entitled “Object-Oriented Workflow for Multi-EnterpriseCollaboration,” and U.S. patent application Ser. No. 09/156,434,entitled “Exemplar Workflow Used in the Design and Deployment of aWorkflow for Multi-Enterprise Collaboration,” all filed Sep. 18, 1998,the disclosures of which are incorporated herein by reference.

TECHNICAL FIELD OF THE INVENTION

This invention relates in general to the field of supply chain,enterprise and site planning and, more particularly, to a method forworkflow communication.

BACKGROUND OF THE INVENTION

Supply chain, enterprise and site planning applications and environmentsare widely used by manufacturing entities for decision support and tohelp manage operations. Decision support environments for supply chain,enterprise, and site planning have evolved from single-domain,monolithic environments to multi-domain, monolithic environments.Conventional planning software applications are available in a widerange of products offered by various companies. These decision supporttools allow entities to more efficiently manage complex manufacturingoperations. However, supply chains are generally characterized bymultiple, distributed and heterogenous planning environments. Thus,there are limits to the effectiveness of conventional environments whenapplied to the problem of supply chain planning due to monolithicapplication architectures. Further, these problems are exacerbated whenthere is no one “owner” of the entire supply chain.

SUMMARY OF THE INVENTION

It is desirable for the next evolutionary step for planning environmentsto establish a multi-domain, heterogenous architecture that supportsproducts spanning multiple domains, as well as spanning multiple enginesand products. The integration of the various planning environments intoa seamless solution can enable inter-domain and inter-enterprise supplychain planning. Further, an important function provided by some planningapplications is the optimization of the subject environment rather thansimply tracking transactions. In particular, the RHYTHM family ofproducts available from I2 TECHNOLOGIES provide optimizationfunctionality. However, with respect to planning at the enterprise orsupply chain level, many conventional applications, such as thoseavailable from SAP, use enterprise resource planning (ERP) engines anddo not provide optimization.

The success or failure of an enterprise can depend to a large extent onthe quality of decision making within the enterprise. Thus, decisionsupport software, such as I2 TECHNOLOGIES' RHYTHM family of products,that support optimal decision making within enterprises can beparticularly important to the success of the enterprise. In general,optimal decisions are relative to the domain of the decision supportwhere the domain is the extent of the “world” considered in arriving atthe decision For example, the decision being made may be how much of agiven item a factory should produce during a given time period. The“optimal” answer depends on the domain of the decision. The domain maybe, for example, just the factory itself, the supply chain that containsthe factory, the entire enterprise, or the multi-enterprise supplychain. (The latter two can be considered to be larger domains ormultiple domains.) Typically, the larger the domain of the decisionsupport, the more optimal the decision will be. Consequently, it isdesirable for decision support software to cover ever larger domains inthe decision making process. One solution is to design workflows whichcan be a set of activities joined by dataflows that together accomplishsome tasks. Workflows can be executed on one or more workflow enginesover one or more enterprises. As workflows run over different enginesand different enterprises the ability to send messages between workflowsor between a workflow and an application or user. What is needed is amethod for communication is disclosed that provides advantages overconventional supply chain, enterprise and site planning environments.

A computer implemented method for workflow communication is provided.The method includes the following steps. First, one or more workflowsare executed. Then an event manger is triggered on the occurrence of apredefined event on the workflow. Finally, a message based on the eventis formulated and sent to a fixed group.

A technical advantage of the present invention is the ability to sendmessages within and between enterprises using either a point-to-point orsubscribe/publish paradigm. Additional technical advantages should bereadily apparent to one skilled in the art from the following figures,descriptions, and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the present invention and advantagesthereof may be acquired by referring to the following description takenin conjunction with the accompanying drawings, in which like referencenumbers indicate like features, and wherein:

FIG. 1 is a diagram of one embodiment of a computer implementedarchitecture that can support enterprise collaboration;

FIG. 2 is a diagram of one embodiment of components of a globalcollaboration framework;

FIG. 3 is a diagram of the global collaboration framework of FIG. 2where certain software elements that make up particular modules arehighlighted;

FIG. 4 is a block diagram of one embodiment of a system allowingcollaboration within and between enterprises for optimal decisionmaking;

FIG. 5 is a block diagram of one embodiment of the use of a globalcollaboration workspace;

FIG. 6 is a diagram of one embodiment of a lifecycle for acollaboration;

FIG. 7 is a diagram of situations where common software is present onboth sides of a relationship and where it is not;

FIG. 8 is a block diagram of one embodiment of a security configurationfor a hub-to-spoke and hub-to-web case;

FIG. 9 is a block diagram of one embodiment of a security configurationfor a hub-to-hub case;

FIG. 10 is a diagram of one embodiment of designing an inter-enterpriseworkflow that includes parameterization over groups;

FIG. 11 is a diagram of one embodiment of managing change be modifying adesign of a workflow;

FIG. 12 illustrates a block diagram of one embodiment of the systemincorporating workflow communication;

FIG. 13 is a block diagram of one embodiment of the event manager;

FIG. 14 illustrates a block diagram of one embodiment of apublish/subscribe communication model;

FIG. 15 is a diagram of one embodiment of integration of a workflow withthe outside world;

FIG. 16 is a diagram of one embodiment of a data flow running in asingle activity;

FIG. 17 is a diagram of one embodiment of a data flow split acrossmultiple activities;

FIG. 18 is a block diagram of one embodiment of an common data modelbased transformation model;

FIG. 19 is a diagram of one embodiment of a direct transformation;

FIG. 20 is a diagram of one embodiment of different access andtransformation levels; and

FIG. 21 is a diagram of one embodiment of substituting a hub engine fora spoke engine within a collaboration.

DETAILED DESCRIPTION OF THE INVENTION

Improvement of decision support processes involves expansion to provideenterprise level and multi-enterprise level decision support for optimaldecision making. Technologically and conceptually, providingenterprise-level and multi-enterprise level decision support differsfrom providing factory-level and supply-chain-level decision support.The reasons for this can be that, in multi-domain situations (such asbusiness units within an enterprise or multiple enterprises), thedifferent domains often operate different decision support software.Also, in multi-domain situations, one domain generally can not coerceanother domain into making a particular decision. In other words,optimal decision support in this environment often needs to be performedin a negotiated, as opposed to coercive, environment.

Providing decision support in multi-domain situations can beaccomplished by pursuing a collaborative approach to decision supportrather than a coercive one. Various communication and distributedprocessing technologies can be used to implement such an environment,including the Internet, the Web, JAVA, XML, CORBA, etc., which help makelarge scale collaborative decision making feasible. Products will soonbe available from I2 TECHNOLOGIES that enable a collaborative approachto decision support, including RHYTHM-GLOBAL COLLABORATION MANAGER (GCM)and RHYTHM-GLOBAL COLLABORATION DESIGNER (GCD).

Collaboration System and Process Components

FIG. 1 is a diagram of one embodiment of a computer implementedarchitecture that can support enterprise collaboration. As shown, aglobal decision support architecture can be built upon underlying link,vision, global messaging and data warehouse components. Collaborationcan then involve a global collaboration designer (GCD) and a globalcollaboration manager (GCM) supported by the decision supportarchitecture. The global collaboration designer can be used to designand instantiate collaborations, and the global collaboration manager canbe used to run the collaborations. In this scheme, collaborations can bereferred to as modules and can be versioned.

FIG. 2 is a diagram of one embodiment of components of a globalcollaboration framework. As shown, the framework can allow an hubenterprise 2 to collaborate with a spoke enterprise 4 and a webenterprise 6. Hub enterprise 2 and spoke enterprise 4 each include aglobal collaboration manager 8. Global collaboration managers 8 arecoupled to and communicate with respective internal global collaborationworkspaces 10. An external global collaboration workspace 12 provides ameans for sharing data between hub enterprise 2, spoke enterprise 4 andweb enterprise 6. Hub enterprise 2 can also collaborate through anelectronic data interchange (EDI) processor 14 with a value addednetwork (VAN). Further, hub enterprise 2 can communicate and collaboratewith other hub enterprises using a global message bus 15.

In operation, the primary controller of the collaboration can be the GCMengine 8 of hub enterprise 2. The hub-to-hub relationship can befacilitated by the global message bus 15, and the hub-to-spoke andhub-to-web relationships can be facilitated by external globalcollaboration workspace (GCW) 12. As shown, a hub enterprise 2 cangenerally have an internal GCW 10 and an external GCW 12. Internal GCW10 can be used to share and exchange data with internal user interfacesas well as EDI processor 14. External GCW 12 can be used to share andexchange data with spoke enterprises 4 and web enterprises.

For security, external GCW 12 can be installed in a DMZ or outside acorporate firewall of hub enterprise 2. This way no direct connectionsneed to be made from the outside into the protected corporate network ofhub enterprise 2. External GCW can accept, for example, IIOP, HTTP andHTTPS connections. In particular, the latter two connections are usefulfor bridging existing firewall configurations. In this manner, nofirewall configuration is needed on either the client (spoke node or webnode) or server (hub node) side which can make the solution more quicklydeployable.

FIG. 3 is a diagram of the global collaboration framework of FIG. 2where certain software elements that make up particular modules arehighlighted. As can be seen, software for the global collaborationmanager module can be present in the following places: in the hub engine8, in the spoke engine 8, in the hub-user user interface (UI), in thespoke-user UI and in the web-node UI. Additionally, the module cancommunicate with native applications 17 on the hub enterprise 2 andspoke enterprise 4. Communications with native applications 17 can beeither synchronous (dot line) or asynchronous (solid line). Asynchronouscommunication with native applications 17 can be facilitated by theinternal GCW's 10, as shown. Further, a global series database (GSDB)can be present on the hub enterprise 2 side.

FIG. 4 is a block diagram of one embodiment of a system, indicatedgenerally at 16, allowing collaboration within and between enterprisesfor optimal decision making. As shown, system 16 includes a hub node 18which can be a process within a hub engine executing on a computersystem. Hub node 18 is coupled to and communicates with a spoke node 20which also can be a process within a hub engine executing on a computersystem. As shown, spoke node 20 can be outside an enterprise boundary 22of hub node 18. Hub node 18 is also coupled to and communicates with aplurality of spoke nodes 24 which can be processes within a spoke engineexecuting on one or more computer systems. Hub node 18 can further becoupled to and communicate with a plurality of web nodes 26 which can beprocesses within a web browser executing on a computer system. Inaddition, hub node 18 is coupled to and communicates with an EDI(Electronic Data Interchange) proxy 28 which can provide a gateway toEDI systems.

Hub engines and spoke engines, together with a global collaborationworkspace, can be the primary entities of a global collaborationmanager. In this environment, a hub engine is the primary controller ofthe collaboration. The hub engine can coordinate both globalcollaborations as well as local collaborations. Global collaborationsare those that span hub nodes 18, spoke nodes 20 and 24 and web nodes26. Local collaborations can run locally on any single role hub orspoke/spoke-group. These collaborations can be distributed, but staywithin the confines of a single enterprise. Hub engines can alsocoordinate with hub-user interfaces (UI) as well as the VAN-EDIprocessor of an EDI proxy 28. In one embodiment, hub engines aremulti-threaded engines that can simultaneously coordinate multiplecollaborations as well as multiple versions of the same collaboration.Further, the hub engines can dynamically load and executecollaborations.

A spoke engine can also operate to initiate a collaboration. In thisenvironment, unlike a hub engine, a spoke engine is not an independententity. Instead a spoke engine can only coordinate a collaboration inconjunction with a hub engine. Furthermore, a spoke engine can notcoordinate with other spoke engines or other web-nodes. Like a hubengine, a spoke engine can be multi-threaded and can simultaneouslycoordinate multiple collaborations as well as multiple versions of thesame collaboration. Spoke engines can also dynamically load and executecollaborations.

FIG. 5 is a block diagram of one embodiment of the use of a globalcollaboration workspace 30. In FIG. 5, global collaboration workspace 30provides the primary entity used to share data/objects between thevarious entities in the collaboration. As shown, workspace 30 caninterface with global collaboration managers (GCMs) 32, a local system34, a web server 36 and web interface 37 and native applications 38. Ingeneral, objects can be placed into global collaboration workspace 30 byone entity and retrieved by another entity. Retrieval can be achievedeither by querying or by subscription. In this way, global collaborationworkspace 30 combines the attributes of a database as well as a messagebus.

The global collaboration workspace can be organized as a hierarchy ofslots which can be in-memory or persistent. Slots also can be queued orregular, and fine grained permissibilities can be attached to each slot.The permissibilities can be assigned by-user-by-operation. The primaryoperations can be read, write, take, and subscribe.

In-memory slots hold their data in volatile memory. Writing andretrieval from in-memory slots is very fast but subject to loss if theglobal collaboration workspace 30 goes down. When used with in-memoryslots, the global collaboration workspace 30 can be considered a fast,secure, in-memory object database, with security and messagingcapabilities. Persistent slots hold their data in stable storage.Writing and retrieval from persistent slots is slower than for in-memoryslots, but data is not lost if the global collaboration workspace 30goes down.

The decision as to whether to use in-memory or persistent slots candepend on the application. Global collaboration workspace 30 stores datain the form of objects and can store Java Objects, CORBA objects orarbitrary byte arrays. This, coupled with its in-memory capabilities,makes global collaboration workspace 30 appropriate as a high-speed datasharing mechanism between other object-oriented in-memory engines suchas I2 TECHNOLOGIES' SUPPLY CHAIN PLANNER and FACTORY PLANNER.

A global collaboration designer (GCD) provides a tool to allowcollaboration designers to interactively design, instantiate and deploycollaborations to be run using the global collaboration manager. Theoutput of the global collaboration designer is code that can beautomatically loaded and run by the global collaboration manager. Theglobal collaboration designer can allow designers to create newcollaborations, retrieve existing collaborations, and versioncollaborations. The global collaboration designer can also allowdesigners to design the hub and spoke network for collaborations anddesign the events and messages of the collaboration. The globalcollaboration designer can integrate a standard object library and. astandard component library for easy usage from within the globalcollaboration designer. The global collaboration designer can be used tocreate sophisticated multi-enterprise workflows with synchronous,asynchronous, sub-workflow, and-splits, or-splits,synchronization-joins, heterocast-splits, heterocast-joins etc. Globalworkflows and local workflows can both be created. The globalcollaboration designer can provide automatic verification ofcollaborations and automatic code generation, which code is run by theglobal collaboration manager. The generated code can be manually editedif desired. Further, the global collaboration designer can provideistantiation of a collaboration including generation of security managerconfigurations and global collaboration workspace configurations.

FIG. 6 is a diagram of one embodiment of a lifecycle for acollaboration. As shown, in step, a collaboration can be designed usingthe global collaboration designer. Then, in step 46, a collaboration canbe instantiated using the global collaboration designer. Theinstantiated collaboration can then be deployed, in step 44, using theglobal collaboration designer and the global collaboration manager.After deployment, the collaboration can be run using the globalcollaboration manager in step 46. Subsequently, a new instance can becreated or a new version of the collaboration can be created. To createa new instance, the flow returns to step 42. For a new version, theglobal collaboration designer can be used in step 48 to modify thecollaboration.

The extension from single-domain decision support to multi-domaindecision support can be complicated. In particular, the followingdiscussion describes a number of challenges presented by multi-domaindecision support and embodiments of how those challenges are addressedby the present system and process allowing collaboration within andbetween enterprises for optimal decision making.

Representational Heterogeneity

One problem with collaboration is bridging representationalheterogeneity across enterprises. Before collaboration can successfullyoccur, the representational heterogeneity across enterprises needs to bebridged. Enterprises often represent the same data in different ways.These differences range from semantic differences, to technologicaldifferences, to differences in naming, etc. One obvious solution tobridging these differences is standardization. However, this immediatelyraises the issue of what standard to agree upon. The present system andprocess avoid such a requirement.

It should be noted that there can be three relevant categories ofstandards that need to be addressed. These three categories are: formatstandards, transport standards and semantic standards. Format standardsrefer to the technological formats in which the data/objects areencoded. Examples include XML, Java Serial Streams, IIOP Serial Streamsand EDI format. Transport standards are used to pass data around. Thesecan include HTTP, IIOP, RMI, DCOM, FTP, Value Added Networks,Asynchronous Message Buses such as MQSeries, etc. Third, semanticstandards are the way in which the semantic content of the data isdescribed. Examples include EDI, I2 COMMON DATA MODEL (CDM).

By considering standards in this light, an understanding of the issuescan emerge. A lot of the confusion today stems from the fact that manyexisting standards cover two or more of the categories above and thatdiscussions of the various standards fail to categorize which categoryis being discussed. For example, EDI is primarily a semantic standard,but also typically implies a format standard (the EDI file format) and atransport (a Value Added Network). Once this is understood, it becomesclear that the EDI semantic standard can be separated from the othertwo. Hence, semantic EDI objects can be encoded in other formats such asJava Serial Streams and can be passed over other transport standardssuch as HTTP. Similarly, XML is primarily a format standard that can beused to encode various semantic standards. Efforts are underway toencode EDI in XML.

Several format standards can be supported by the present globalcollaboration manager, including XML, EDI format, Java Serial Streams(referred to as Java format and not to be confused with the JavaLanguage or Java Platform) and IIOP Serial Streams. Of these, in oneembodiment, the Java format is the primary format, and the rest arederived formats. Because the Java Format can contain the behavior toproduce the other formats, it has been chosen as the primary format.XML, EDI and IIOP formats can be derived from the Java Format.

FIG. 7 is a diagram of situations where common software from I2TECHNOLOGIES' is present on both sides of a relationship and where it isnot. As shown, for example, when RHYTHM GLOBAL COLLABORATION MANAGER ison both sides, nothing is to be gained by converting to an intermediateformat. This would introduce needless inefficiency, and only data (notobjects) would be exchangeable, limiting the range of applications.Hence when the same software is present on both sides, binary Javaobjects can be directly exchanged. On the other hand, for example, whenRHYTHM GLOBAL COLLABORATION MANAGER is present only on one side, XML orEDI-formatted “objects” can be produced (outbound) and interpreted(inbound).

With respect to transport standards, the present global collaborationmanager can support a variety of transport standards, including HTTP,IIOP, and Asynchronous Message Buses. More details are provided belowwith respect to Handling Multiple Relationship Types.

With respect to semantic standards, the present global collaborationmanager can primarily support two semantic standards, EDI andRHYTHM-CDM. EDI can be supported because it is generally the mostpopular semantic standard. However it suffers from the drawback (amongstothers) of not providing deep coverage of the planning domain. TheRHYTHM-CDM, on the other hand, provides deep coverage of the planningdomain and will provide appropriate constructs for performingmulti-enterprise decision support. Additionally, this format issupported by all of I2 TECHNOLOGIES' planning engines.

In general, one problem with public standards, such as EDI, is that theymay not adequately cover the kinds of data/objects that enterpriseswould like to exchange. Further, waiting for standards bodies tostandardize on a particular object may not be an option, and a supplychain will not have any particular competitive advantage by using publicstandards. For these and other reasons, the present global collaborationmanager supports an alternative approach to standardization bysupporting proprietary community standards. For example, usingRHYTHM-GCD, a community of enterprises can devise a set of standardsthat are relevant to that community only. RHYTHM-GCM will support andenforce these proprietary community standards. RHYTHM-GCD also supportsa library of building block objects that can be composed intoproprietary community standards. Proprietary community standards have anumber of advantages, including: they can be designed to exactly coverthe kinds of data/objects that enterprises would like to exchange; onlythe relevant parties need to agree upon the particular standard, hencethe process will be much quicker than waiting for a standards body;different standards can be developed for different categories ofpartners and, in the extreme case, a different standard for eachpartner; and standards that give the supply chain a competitiveadvantage over competitors can be developed.

Multiple Relationship Types

Another problem for allowing collaboration is handling multiplerelationship types. Enterprises have relationships of various types withtheir partners. Some ways relationships can vary are: between majortrading partners on the one hand and between minor trading partners onthe other; between enterprises of roughly equal influence over thesupply chain and between enterprises of unequal influence over thesupply chain; and between enterprises with a high degree oftechnological sophistication on the one hand and between enterpriseswith an unequal degree of technological sophistication on the other. Asshould be understood, these different relationship types should behandled differently.

The present global collaboration manager can model enterpriserelationships as a hub and spoke network, as described above and shownin FIG. 4. In this embodiment, the four types of relationships are:Hub-to-Web; Hub-to-Van-EDI; Hub-to-Spoke and Hub-to-Hub. Eachrelationship-type has its appropriate usage.

With respect to Hub-to-Web, when people speak of E-Commerce today, theyoften imply an architecture where a web browser talks to somecentralized server. This architecture has some advantages: theinfrastructure to support this architecture is typically already inplace; and all administration can be centralized on the server side.However, this architecture also has a big disadvantage in that itrequires the presence of a human on the web-browser side. Hencesystem-to-system automation is not possible. Based on these and otherpros and cons, this relationship type can be appropriate when anenterprise needs to exchange data with either a minor partner or apartner with less technological sophistication.

With respect to Hub-to-VAN-EDI, the vast majority of electronicinter-enterprise commerce takes place today by sending EDI over ValueAdded Networks. The advantage of this approach can be thatsystem-to-system integration is possible and it is currently supportedtoday. Disadvantages of this approach are: large costs to send data overproprietary VAN's; high administrative costs because of lack of truestandardization; requirement for third party tools just to convert fromthe true “standard” to a form appropriate for the enterprise; no supportfor system-to-human integration; and no support for proprietarystandards or corporate standards. Based on these and other pros andcons, this relationship type can be appropriate when supporting a legacyVAN-EDI environment.

With respect to hub-to-spoke, this relationship type also enablessystem-to-system integration like VAN-EDI. Architecturally hub-to-spokeis a collaboration between a hub engine and a spoke engine. Thehub-to-spoke relationship can have advantages vis-a-vis VAN-EDI: it canuse the public Internet to reduce network costs; administrative costsare much lower than VAN-EDI because a large portion of the hub-to-spokerelationship infrastructure can be centrally deployed and administered;true objects (in addition to just data) can be exchanged allowing formuch more advanced collaborations; and multiple semantic standards canbe supported including EDI, I2-CDM and Proprietary Community Standards.Based on the characteristics above, the hub-to-spoke relationship can beappropriate between enterprises that wish to perform sophisticatedsystem-to-system collaboration. It can also be appropriate where no I2TECHNOLOGIES' software is present in either of the enterprises. This isbecause the hub-to-spoke relationship can be centrally deployed by thehub enterprise.

With respect to hub-to-hub, the relationship is similar to hub-to-spokeexcept that it takes place between two hub engines rather than a hub anda spoke engine. Based on this characteristic, the hub-to-hubrelationship can be appropriate between enterprises that wish to performsophisticated system-to-system collaboration. Further, the hub-to-hubrelationship can be appropriate when two enterprises have individuallyand separately purchased RHYTHM-GCM and have set up hub engines.

There are differences between hub engines and spoke engines. In general,a hub engine'scapabilities are a superset of a spokeengine'scapabilities. The following table provides an example of some ofthe differences.

TABLE 1 Spoke Engine Hub Engine Purchasing and Spoke engines are Soldseparately. Deployment bundled with a hub engine. Hence a hub enterprisewill typically purchase a hub engine and a number of spoke engines whichit can deploy out to its partners. Relationship Can only support theSupports types supported hub-to-spoke hub-to-hub, relationship.hub-to-spoke, Additionally, each hub-to-web and spoke engine canhub-to-VAN-EDI only communicate relationship with a particular types.hub engine (its owning hub). Authoring Can view but not Can view andCollaborations author a author a collaboration. collaboration.Internal-User Supports a single Supports multiple Roles. internal-userrole. internal-user roles.

Security

A further problem with collaboration is the challenge of providingcomprehensive security.

Before enterprises can collaborate effectively, the security issue needsto be addressed. There are many different facets to security in acollaborative context. Any multi-enterprise collaborative frameworkshould address all of these different facets. The requirements for acollaborative security framework can include that: data exchangedbetween two partners should only be seen by the two partners; dataexchanged between two partners should be tamper-proof; an enterpriseshould be able to verify that a partner is who it claims to be; theframework should not introduce new security holes into a partners'network; and the framework should be relatively easy to set up andadminister.

A secure collaborative framework can be provided by implementing acomprehensive security strategy to address the above requirements. Inone embodiment, the strategy has three different aspects to it:technological security, a permissibility framework and datapartitioning.

Technological security can refer to the technological means used toguarantee security. This security can be used to provide: privacy,authentication and data integrity. Privacy ensures that no unauthorizedperson can see the data. Authentication involves authenticating that theparties in the collaboration are really who they claim to be. DataIntegrity involves making it impossible for an unauthorized person tomodify data being sent in any fashion.

The precise security approach can vary based on the relationship typedescribed earlier. For example, one scheme is detailed in the tablebelow:

TABLE 2 Relationship Technological Provided Type Approach By Hub-to-webHTTP-over-SSL 3.0 Global Collab (e.g., Workspace Diffie-Helman)HTTP-over-SSL 3.0 (e.g., RSA) IIOP-over-SSL 3.0 Global Collab WorkspaceHub-to-spoke HTTP-over-SSL 3.0 Global Collab (e.g., WorkspaceDiffie-Helman) HTTP-over-SSL 3.0 Global Collab (e.g., RSA) WorkspaceIIOP-over-SSL 3.0 Global Collab Workspace Hub-to-hub TCP/IP-over-SSLGlobal Message 3.0 Bus Content-based Global Message Encryption BusHub-to-VAN EDI Security handled VAN by VAN.

As can be seen from the table, all of the relationship types, with theexception of Hub-to-VAN EDI, could support security via SSL 3.0.

SSL 3.0 is an industry standard protocol used to support public keyencryption over a socket-based connection and provides: privacy, clientas well as server authentication, data integrity and certificatemanagement. SSL 3.0 is a higher level protocol into which severalpublic-key cryptography algorithms can be plugged including RSA andDiffie-Helman.

Once the SSL handshake is complete, the next step is username-passwordauthentication. This provides authentication beyond what SSL 3.0 itselfprovides. Passwords can be stored using PKCS5 password-based encryption(an RSA standard). Once a user or spoke is authenticated, it is returnedan Access Token. This access token has an administrator-specifiablelifetime. A user can then access the system for the duration of validityof the access token. This has the beneficial effect of not requiringauthentication on each access. Each application which is accessed,authenticates the access token by validating the signature (which is adigest encrypted using the Security Manager's private key) of theSecurity Manager.

The technological security framework is a portion of the securityscheme. The other portion has to do with the design of thecollaborations themselves. The framework should allow enterprises toeasily attach permissibilities to various actions that other enterprisescan perform on it. The global collaboration workspace can support ahierarchical permissibility model with individual permissibilitiesattached to different data elements in the hierarchy. In particular, itcan support user-specific and spoke-specific read, write, take andsubscribe permissibilities. Hence, enterprises can finely tune who canread what data, who can write what data, who can take what data and whocan subscribe to write-notifications on what data.

A third element in the collaboration framework security strategy is theability to partition data across various collaborative workspaces. Inparticular, the collaborative workspaces are split into an internalcollaborative workspace and an external collaborative workspace. Onlydata that needs to be truly shared with partners is in the externalcollaborative workspace. The rest is in the internal collaborativeworkspace. The external collaborative workspace is designed to siteither outside the corporate firewall or in an Extranet or DMZ. Thecollaboration framework design does not require the externalcollaborative workspace to make connections through the corporatefirewall into the Intranet (although it could).

In one embodiment, global collaborations can use both the external andinternal collaborative workspaces. Local collaborations can use only theinternal collaborative workspace and are hence completely invisible topartner enterprises. Even for global collaborations only the relevantportions use the external collaborative workspace. Furthermore, becauseof the permissibility framework described earlier, each partnerenterprise can only see (read, write, take, subscribe) to its own data.

FIG. 8 is a block diagram of one embodiment of a security configurationfor a hub-to-spoke and hub-to-web case. As shown, a hub enterprise 50 iscoupled to and communicates with an internal global collaborationworkspace 52 and an external global collaboration workspace 54. A spokeenterprise 56 and a web enterprise 58 connect through a web server 60 tothe external global collaboration workspace 54. Spoke enterprise 56,like hub enterprise 50, has an internal global collaboration workspace62. The enterprises 50, 56 and 58 can be protected by associatedfirewalls, while the extranet formed by web server 60 and externalglobal collaboration workspace 54 can be protected by a filtering routerand communication via HTTP over SSL 3.0.

FIG. 9 is a block diagram of one embodiment of a security configurationfor a hub-to-hub case. As shown, a hub enterprise 64 and a hubenterprise 66 can communicate across an SSL 3.0 protected TCP/IPconnection. The communication can be between separate global messagebrokers 68 and 69. Both hub enterprises 64 and 66 are protected by afirewall, as shown.

Inter-Enterprise Workflows

One of the problems with multi-enterprise decision support can be thatthere is no closed loop collaboration. Instead, data may be lobbed fromone enterprise to the next with no coherent workflow. In order toimplement closed loop collaboration, support for creatingmulti-enterprise workflows is necessary. The present globalcollaboration manager and designer can make it possible to construct,deploy, monitor and change sophisticated multi-enterprise workflows.

In general, a “workflow” can be a set of “activities” joined together bydata flows that together accomplish some task. Workflows are typicallyexecuted on workflow engines. A “distributed workflow” can refer to aworkflow that is executed on multiple workflow engines. In other words,different portions of the workflow execute on different engines. A“node” can refer the abstract entities on which different workflowengines of a distributed workflow run, and a “node group” can be a setof nodes grouped by some characteristic. A “multi-enterprise distributedworkflow” can be distributed workflows where the nodes are enterprises.

Parameterization of workflows can be important for enterprisecollaboration. A “parametric workflow” is a workflow that isparameterized over some variable and can be regular or distributed.Instantiating the parametric workflow with different values of theparameter variable(s) produces different instances of the workflow. A“distributed workflow parameterized over nodes in a node group” canrefer to distributed workflows where the parameters of the workflow arethe nodes in a node group. Hence, when the workflow is instantiated itis tailored to a particular node in a node group.

There are several important features to the workflows that can besupported by the present global collaboration. These workflows can bestrongly typed. Strong typing can be essential in producing robust,error-free workflows. In essence, strong typing guarantees the type of amessage at design time. For example, if the workflow is designed to senda Bill of Materials, then strong typing ensures that is physicallyimpossible that an object other than a Bill of Material is sent. For aworkflow designed with the global collaboration designer and executedwith the global collaboration manager, it can be made impossible to evensend an object of an incorrect type. This capability is important toproducing robust, error-free workflows.

Despite strong typing, there are, for example, two scenarios in whichwrong object types could conceivably be passed in the workflow: due toan error on the workflow designer's part; and a malicious attempt bysomeone to undermine the workflow. Both of these scenarios can behandled. The first can be handled by making it impossible for an errorin design to lead to such a scenario. The second can be handled bymaking the data flows tamper-proof by using public key cryptography orother encryption scheme (integrity characteristic) as described above.

Another important feature is support for workflows parameterized overgroups. Some multi-enterprise workflows involve a large number ofenterprises. In such cases it can become impractical to createindividualized workflows for each partner. Instead it can beadvantageous to create workflows that are parameterized over groups ofpartners. For example, in the realm of procurement, two groups may beprimary suppliers and secondary suppliers. The primary suppliers groupcould have one type of workflow, and the secondary suppliers group couldhave another type of workflow. Group-based workflows can be parametricin the sense that, at run time, an actual workflow can be createdspecific to a member of a group.

In the multi-enterprise context, an enterprise may collaborate, forexample, with potentially hundreds or thousands of other enterprises.Each collaboration or multi-enterprise workflow can be potentially (andtypically) unique. However, designing thousands of specialized workflowswith an enterprises' partners is neither desirable nor feasible. On theother hand, many of these workflows are simply parametric variations onan underlying parameterized workflow. For example, a company A may becollaborating (on sales) with retailers, distributors, direct sales etc.Hence, it makes sense to group the various partners. An example groupingmay be: WalMart; Sears; Rest of Retailers besides WalMart and Sears(group); Primary Distributors (group) and Secondary Distributors(group). Now, the workflows with all the members, for example, of theprimary distributors group are variations on an underlying parametricdistributed workflow, parameterized over the particular distributor inthat group.

Workflows parameterized over groups can be supported by a HETEROCASTINGworkflow definition technique. The HETEROCASTING definition techniquegenerally involves using a parameterized workflow definition toinstantiate heterogeneous workflows based upon differences in theparameters. Thus, the HETEROCASTING definition technique allows anon-parametric distributed workflow to be easily (through a visualdesign tool) be made parametric over nodes in a node group. There can betwo primary workflow activities used to accomplish this definition: aHETEROCAST split activity and HETEROCAST join activity. All activitiesbetween a HETEROCAST split and a HETEROCAST join are parameterized overthe nodes of a node group that these activities correspond to.

FIG. 10 is a diagram of one embodiment of designing an inter-enterpriseworkflow that includes parameterization over groups. As shown, theworkflow can begin with a listening activity 70 that waits for someevent. Activity 70 can be linked to parallel activities 71 that links toa sub-workflow 72 and to a heterocast split 73. Sub-workflow, itself,can include a workflow definition. With respect to HETEROCASTING, theworkflow after heterocast split 73 then becomes parameterized. Thus, inthe example of FIG. 10, activity 74 is a parameterized activity. Afteractivity 74, a heterocast join 75 receives flow from activity 74.Sub-workflow 72 and heterocast join 75 are linked to a synchronous orasynchronous join 76 which, in turn, links to an integrated event 77(e.g., multicasting). A workflow like that of FIG. 10 can be designedusing the present global collaboration designer and can allow fullrepresentation of workflow for inter-enterprise decision support. Thisworkflow can then be instantiated and implemented through the presentglobal collaboration manager.

FIG. 11 is a diagram of one embodiment of managing change be modifying adesign of a workflow. As shown, an initial workflow design can have anevent 70 linked to a parallel activity split 71. Between activity split71 and a join 76, there can be, for example, two activities 78. Thiswork flow, once designed, can be instantiated and implemented using theglobal collaboration manager. If a change needs to be made to theworkflow, the global collaboration designer greatly alleviates thetrouble of making the change. For example, a new activity 79 can beadded between split 71 and join 76. The workflow can then be centrallyreinstantiated and implemented.

In particular, the HETEROCAST technique can allow the construction ofdistributed workflows parameterized over nodes in a node group. This canallow a huge productivity gain over designing individual workflows forindividual group members. Further, this technique makes rapid design andprototyping of sophisticated inter-enterprise workflows with hundreds orthousands of partners feasible. The technique should be distinguishedfrom conventional “multicasting” in which identical messages are sentout to the various nodes (partners). In essence, multicasting allows youto design a single workflow that runs identically across multiple nodes.This differs from the HETEROCASTING technique, where the workflows rundifferently based on which node they are running across.

A third important feature is support for role-based workflows.Role-based workflows allow workflows to be specified using genericroles. This capability allows the creation of generic or templatedworkflows that can be instantiated in various scenarios. For example,the role types can be: partner roles, spoke roles; spoke group roles;web roles; web group roles; user roles. As an example of roles, partnerroles refer to the different roles played by partners. Thus, one partnerrole in the case of procurement is primary supplier and secondarysupplier.

Role-based workflows can lead to the concept of three different phasesin the design and execution of a workflow. The design phase is the phasein which role-based workflows are defined. The instantiation phase isthe phase in which roles are mapped to instances. For example, primarysupplier may be mapped to a first company, and PO_approver may be mappedto John Doe. Third, the run time phase can be the phase in which theinstantiated workflow runs.

A further important feature is the integration of automated workflowswith user-oriented workflows. Workflows can often be described as havingtwo varieties: automated system-to-system workflows, and user interfaceworkflows. While there are workflows that are completely automated, andthere are workflows that are completely user driven, most workflows haveautomated as well as user interface elements. The present globalcollaboration manager and designer do not need to make this artificialdistinction between workflow types. Hence, the workflows can beautomated in parts and interact with users in other parts. Both theautomated parts and user parts can span multiple enterprises.

A further important feature is workflow communication. Communication canoccur across enterprises triggered by events occurring in a workflow.Communication can take one of two forms: point-to-point communicationand subscribe/publish communication. In a point-to-point communicationscheme individual messages are sent to each intended recipient. Forexample, if there are 10 people who need to be contacted, 10 messagesare sent to those people. In a publish and subscribe scheme, individualssubscribe to receive messages which are generated by an event. When theevent occurs, a message is sent to all users who had subscribed.

FIG. 12 illustrates a block diagram of one embodiment of the systemincorporating workflow communication. System 16 includes a Hub 17 whichincludes a hub engine 19. Hub engine 19 includes an even manager 200.Coupled to Hub 17 are spoke nodes 24 which can include processes such asworkflow running on spoke engines. Additional spoke nodes 20 can becoupled to hub 17.

In operation spoke nodes 24 may be operable to receive point-to-pointcommunications from hub 17. When a workflow executing on hub engine 19reaches a certain event, event manager 200 may be triggered to sendindividual messages to spoke nodes 24 in a point-to-point scheme.Additionally, spoke node 20 may subscribe to event manager 200 toreceive messages at certain times based on events reached by workflowrunning on engine 19. When the event is reached, event manager 200 alongwith a message handler (not pictured) will send messages to allsubscribers. For example, an event can be the arrival of an invoice.When the invoice arrives, all subscribers will receive notice.

FIG. 13 is a block diagram of one embodiment of the event manager 200.Event manager 200 is coupled to a workflow manager 202. Workflow manager202 is associated with one or more modules 203. Modules 203 are coupledto internal workspace 204 where date and objects can be stored for useby an engine. Workflow manager 202 is also coupled to a message handler206 which is operable to receive messages from modules and transmitmessages to external workspaces. Message handler 206 is coupled toexternal workspace 208 where data and objects can be exchanged betweendifferent entities in a collaboration. CORBA interfaces 201 are providedto allow a variety of different programming languages (such as C++ andJava) to access various components.

In operation an event occurring in a workflow running on an engine maytrigger event manager 208 to start a workflow by access workflow manager202. Additionally, any event occurring in a workflow can triggerworkflow manager 202 to access event manager 200. Event manager 200 canthen notify all subscribers that the event occurred. Notificationscontain parameterized data specific to this instance of the event.

FIG. 14 illustrates a block diagram of one embodiment of apublish/subscribe communication model. Illustrated is event manager 200coupled to, and in communication with a plurality of GUI/applications212, 214, and 216. Event manager 200 is also coupled to a module 204which is operable to run a workflow 210.

In operation, first GUI/application 212 sends an event 218 to eventmanager 200. When event 212 is received by event manager 200 it ispasses to a module 204 where it triggers execution of workflow 210. Whenworkflow 210 reaches a point it generates a second event 200. This isthen sent to event manager 200. Event manager 200 then notifies messagesinforming GUI/Application 212, 214, and 216 that the event occurred.Parameterized values specific to the event are sent along withnotifications as long as they are subscribers to the event manager 200.

Integration with Outside World

FIG. 15 is a diagram of one embodiment of integration of a workflow withthe outside world. As described in the previous section, sophisticatedinter- and intra-enterprise workflows can be created. These workflowscan be composed of activities strung together in various configurations.There is no restriction on what the different activities of the workflowcan do, yet one of the major tasks of these activities is to integratewith the outside world. FIG. 15 shows how a workflow can be integratedwith the outside world using a component-based approach to integration.The components can include accessors 80, transformations 82, transferobjects 84, adaptors and flows 86.

The global collaboration manager can support a component-basedintegration model. The component-based integration model allowsflexibility in structuring the integration. There can be two types ofcomponents: primitive components and compound components. Primitivecomponents can include accessors 80, transformers 82 and transferobjects 84. Compound components include adaptors and flows 86. Compoundcomponents are built in terms of primitive components. In this scheme,accessors 80 are used to access an external source such as SCP (SUPPLYCHAIN PLANNER), SAP, a relational database, web servers, email, messagebuses etc. Accessors 80 can be used to read, write or listen to sourcesand destinations of data. Transformers 82 can be used to transform datafrom one form to another form. Transfer Objects 84 are objects that canbe passed from activity to activity or from enterprise to enterprise.Transfer objects 84 can be optionally convertible to EDI, XML, CORBAstructures etc. Accessors 80 and Transformers 82 can be strung togetherto form flows. An entire flow can be executed in a single activity asshown in FIG. 16.

FIG. 16 is a diagram of one embodiment of a data flow running in asingle activity 92. As shown, a data source 90 can be accessible fromand provide data to an accessor component 94. Accessor component 94 thencan pass data through transformer components 96 and 98 which providedata to a second accessor component 100. Data can then be stored in adata destination 102.

FIG. 17 is a diagram of one embodiment of a data flow split acrossmultiple activities 104 and 106. As shown, the flow of FIG. 17 differsfrom that of FIG. 16 in that transformer components 96 and 98 are withinseparate activities 104 and 106 and communicate by a transfer object.Multi-enterprise data flows can be based on the model of FIG. 17 ratherthan that of FIG. 16.

With respect to transformations, in one embodiment, two fundamentaltransformation types can be supported: I2-CDM based transformations anddirect transformations. I2-CDM based transformations are based on I2TECHNOLOGIES' COMMON DATA MODEL (CDM). The CDM is an abstract schemathat is available in both relational and object forms.

FIG. 18 is a block diagram of one embodiment of an I2-CDM basedtransformation model. As shown, transformers and accessors can becoupled to transform a application data into a CDM data object 110 andvice versa. For example, a SUPPLY CHAIN PLANNER (SCP) object 112 can becreated by an SCP accessor from SCP data 114. SCP object 112 can then betransformed by an SCP-CDM transformer into a CDM object 110.Analogously, an SAP object 116 can be created by an SAP accessor fromSAP data 118. SAP object 116 can then be transformed by an SAP-CDMtransformer into a CDM object 110. The SAP accessor and transformer, aswith other accessors and transformers, can be combined into a standardSAP-CDM adapter 120 that can be used for CDM-based transformations othercomponents. As another example, a BAAN object 122 can be created by aBAAN accessor from BAAN data 124. BAAN object 122 can then betransformed into a CDM object 110 by a BAAN-CDM transformer. Thesetransforms work in the other direction as well.

FIG. 19 is a diagram of one embodiment of a direct transformation. Indirect transformers, objects are converted from one form to anotherwithout passing through an intermediate format. For example, as shown inFIG. 19, SUPPLY CHAIN PLANNER (SCP) data 130 can be accessed by an SCPaccessor to create an SCP object 132. SCP object 132 can then bedirectly transformed to a FACTORY PLANNER (FP) object 134. FP object 134can then become FP data 136 through an FP accessor. This data flow canoperate in the other direction as well.

In these processes, there are various levels of granularity at whichaccess and transformation can take place including the relational(table), generic object (tree, graph, matrix etc.) and specific object(Bill of Material, Plan etc.) levels. Sometimes access may only beavailable at one level (say tables), but transformation may be moreappropriate at another level (say generic object). For example,hierarchical aggregation (a form of transformation) is often appropriateon a tree object. However, the data may only be accessible in a tabularform. In this case, for example, the data should be accessed at thetabular level, transformed into a tree, and then have the hierarchicalaggregation applied to it.

FIG. 20 is a diagram of one embodiment of different access andtransformation levels. As shown, access and transformation can havethree levels. A first level 140 can involve table access and transforms.A second level 142 can involve generic object (tree, graph, etc.) accessand transforms, and a third level can involve specific object(build-of-materials, plan, etc.) access and transforms. In additional totransforms between application formats, there can also be transformsbetween the three levels, as shown.

Deployment of Collaborations

One important factor in a multi-enterprise collaboration system is theease with which the collaboration can be deployed. As discussed, thepresent global collaboration manager can support four different kinds ofpartner relationships: hub-to-web, hub-to-spoke, hub-to-hub andhub-to-VAN-EDI. Of these four, hub-to-web has all the deployabilitycharacteristics of traditional web applications. Hub-to-VAN EDI can bedeployable to the extent that it leverages an existing VAN-EDIinfrastructure. While the hub-to-web relationship is highly deployable,it can suffer from the problem of requiring a human on the web side ofthe relationship. In other words, it may not be suited tosystem-to-system collaboration.

The hub-to-spoke solution can provide maximal deployability in thesystem-to-system collaboration environment. In the hub-to-spoke realm,the spoke engine is analogous to the web browser, and the spoke portionof the collaboration is analogous to a web page or applet. Similar to aweb-page or applet, the spoke portion of the collaboration can becentrally designed and deployed to the remote spoke engines. Unlike aweb-page or applet, there may still be integration that needs to be doneremotely. This remote integration may be unavoidable but can becircumscribed and precisely defined by the spoke portion of thecollaboration.

Another aspect of deployability is handling versioning. Collaborationsonce designed and deployed are likely to need changing (in variousdifferent ways) as time progresses. It can be important that subsequentversions of collaborations be as easily deployable as initial versions.The present global collaboration manager can provide complete supportfor versioning and centralized redeployment of collaborations. Further,different versions of collaborations can be run simultaneously withoutimpacting each other. This allows an existing version to be gracefullyphased out while another version is phased in.

Another element of the deployability of the present global collaborationmanager is the leverage of existing infrastructure. This element isevident, for example, in the support of the hub-to-spoke relationshipover existing web protocols. Supporting hub-to-spoke over existing webprotocols can be important to rapid deployment since it does not requiremodification or reconfiguration of an existing web infrastructure. Alarge time savings in this regard can come from not having to modifycarefully designed firewall and security infrastructures that mayalready be in place.

Supporting Many-To-Many Collaborations

The present hub-and-spoke architecture provides easy manageability anddeployment. However, in practice enterprises collaborate with manyenterprises which in turn collaborate with still other enterprises.Hence, enterprises often form a collaborating web or graph. This can besupported via the ability to substitute a hub engine for a spoke engineat any time. This substitution ability allows many-to-many collaborationwebs to be grown organically rather than all at once.

FIG. 21 is a diagram of one embodiment of substituting a hub engine fora spoke engine within a collaboration. As shown, an enterprise (E1) maydeploy a hub engine 150 on itself and a spoke engine 152 at all of itspartner sites. In particular, a spoke engine 154 may be at a partnersite (E2). If the partner site (E2) wishes to design and control its owncollaborations, it can replace spoke engine 154 with a hub engine 156.From E1's perspective, E2 can still be a spoke in E1's collaboration.However, this spoke now runs on a hub engine 156 which can control itsown collaborations with spoke engines 158. Further, spoke engines 160and 162 might be associated with a third entity (E3) that interacts withboth hub engine 150 and hub engine 156 on behalf of E3.

Extension of Framework

An important aspect of the present framework is extensibility. Withoutextensibility, the framework may not be able to handle new situationsand challenges with which it is confronted. There can be severaldifferent dimensions to this extensibility. For example, one primaryarea of extensibility is in the area of semantic object standards. Ifsupported standards do not suffice for a particular problem, then theframework can be augmented with new semantic standards. Additionally theframework allows the building of proprietary semantic standards.Further, the framework can be extended by adding new accessors,transformers, adapters, etc. The standard component library can beextended both generally and by end-users.

Although the present invention has been described in detail, it shouldbe understood that various changes, substitutions and alterations can bemade hereto without departing from the spirit and scope of the inventionas defined by the appended claims.

What is claimed is:
 1. A method for multi-enterprise workflowcommunication, comprising: executing at least a portion of a workflow ata first enterprise; in response to execution of the at least a portionof the workflow at the first enterprise, triggering a workflow managerat the first enterprise operable to manage operations associated withthe workflow and to access an event manager at the first enterprise onan occurrence of a predefined event in the workflow; and based on thatoccurrence of the event and according to a first underlyingparameterized workflow, communicating a plurality of messages from theevent manager at the first enterprise to a particular group of aplurality of second enterprises with which the first enterprisecollaborates to notify the second enterprises in the particular group ofthat occurrence of the event: the first underlying parameterizedworkflow requiring for its operation parameterized data sufficient toparticularize the first underlying parameterized workflow, eachparticularization of the first underlying parameterized workflowaccording to associated parameterized data comprising a separateinstance of the first underlying parameterized workflow; the particulargroup of second enterprises being one of a plurality of groups of secondenterprises, the first underlying parameterized workflow beingparticular to the particular group of second enterprises; the messagesbeing communicated substantially simultaneously to the secondenterprises in the particular group; each message being communicated toa corresponding one of the second enterprises in the particular groupaccording to a corresponding instance of the first underlyingparameterized workflow, the corresponding instance being particular tothe corresponding one of the second enterprises in the particular group;each message containing parameterized data specific to that occurrenceof the event and also specific to the corresponding one of the secondenterprises in the particular group, the parameterized data in themessage sufficient to particularize the first underlying parameterizedworkflow to yield the corresponding instance; each message beingcommunicated to the corresponding one of the second enterprises in theparticular group across an enterprise boundary of the first enterpriseand across an enterprise boundary of the corresponding one of the secondenterprises in the particular group; and based on that occurrence of theevent and according to a second underlying parameterized workflowdifferent from the first underlying parameterized workflow, initiatingan instance of the second underlying parameterized workflow.
 2. Themethod of claim 1, wherein the message is sent only to secondenterprises in the group that have subscribed to receive such messages.3. The method of claim 1, wherein the message is sent individually toall the second enterprises of the group in a point-to-point manner. 4.The method of claim 1, wherein the event comprises the arrival at thefirst enterprise of a business document.
 5. The method of claim 1,wherein the workflow comprises an automated system-to-system workflow.6. The method of claim 1, wherein the workflow comprises auser-interface work flow.
 7. A system for multi-enterprise workflowcommunication, comprising: a workflow manager at a first enterpriseoperable to manage operations associated with execution of at least aportion of a workflow at the first enterprise and to access an eventmanager at the first enterprise on an occurrence of a predefined eventin the workflow; and the event manager at the first enterprise operableto, based on that occurrence of the event and according to a firstunderlying parameterized workflow, communicate a plurality of messagesto a particular group of a plurality of second enterprises with whichthe first enterprise collaborates to notify the second enterprises inthe particular group of that occurrence of the event: the firstunderlying parameterized workflow requiring for its operationparameterized data sufficient to particularize the first underlyingparameterized workflow, each particularization of the first underlyingparameterized workflow according to associated parameterized datacomprising a separate instance of the first underlying parameterizedworkflow; the particular group of second enterprises being one of aplurality of groups of second enterprises, the first underlyingparameterized workflow being particular to the particular group ofsecond enterprises; the messages being communicated substantiallysimultaneously to the second enterprises in the particular group; eachmessage being communicated to a corresponding one of the secondenterprises in the particular group according to a correspondinginstance of the first underlying parameterized workflow, thecorresponding instance being particular to the corresponding one of thesecond enterprises in the particular group; each message containingparameterized data specific to that occurrence of the event and alsospecific to the corresponding one of the second enterprises in theparticular group, the parameterized data in the message sufficient toparticularize the first underlying parameterized workflow to yield thecorresponding instance; each message being communicated to thecorresponding one of the second enterprises in the particular groupacross an enterprise boundary of the first enterprise and across anenterprise boundary of the corresponding one of the second enterprisesin the particular group; and the workflow manager at the firstenterprise operable to, based on that occurrence of the event andaccording to a second underlying parameterized workflow different fromthe first underlying parameterized workflow, initiate an instance of thesecond underlying parameterized workflow.
 8. The system of claim 7,wherein the message is sent only to second enterprises in the group thathave subscribed to receive such messages.
 9. The system of claim 7,wherein the message is sent individually to all the second enterprisesof the group in a point-to-point manner.
 10. The system of claim 7,wherein the event comprises the arrival at the first enterprise of abusiness document.
 11. The system of claim 7, wherein the workflowcomprises an automated system-to-system workflow.
 12. The system ofclaim 7, wherein the workflow comprises a user-interface workflow. 13.Software for multi-enterprise workflow communication, the software beingembodied in a computer-readable medium and when executed operable to:execute at least a portion of a workflow at a first enterprise; inresponse to execution of the at least a portion of the workflow at thefirst enterprise, trigger a workflow manager at the first enterpriseoperable to manage operations associated with the workflow and to accessan event manager at the first enterprise on an occurrence of apredefined event in the workflow; and based on that occurrence of theevent and according to a first underlying parameterized workflow,communicate a plurality of messages from the event manager at the firstenterprise to a particular group of a plurality of second enterpriseswith which the first enterprise collaborates to notify the secondenterprises in the particular group of that occurrence of the event: thefirst underlying parameterized workflow requiring for its operationparameterized data sufficient to particularize the first underlyingparameterized workflow, each particularization of the first underlyingparameterized workflow according to associated parameterized datacomprising a separate instance of the first underlying parameterizedworkflow; the particular group of second enterprises being one of aplurality of groups of second enterprises, the first underlyingparameterized workflow being particular to the particular group ofsecond enterprises; the messages being communicated substantiallysimultaneously to the second enterprises in the particular group; eachmessage being communicated to a corresponding one of the secondenterprises in the particular group according to a correspondinginstance of the first underlying parameterized workflow, thecorresponding instance being particular to the corresponding one of thesecond enterprises in the particular group; each message containingparameterized data specific to that occurrence of the event and alsospecific to the corresponding one of the second enterprises in theparticular group, the parameterized data in the message sufficient toparticularize the first underlying parameterized workflow to yield thecorresponding instance; each message being communicated to thecorresponding one of the second enterprises in the particular groupacross an enterprise boundary of the first enterprise and across anenterprise boundary of the corresponding one of the second enterprisesin the particular group; and based on that occurrence of the event andaccording to a second underlying parameterized workflow different fromthe first underlying parameterized workflow, initiate an instance of thesecond underlying parameterized workflow.
 14. The software of claim 13,wherein the message is sent only to second enterprises in the group thathave subscribed to receive such messages.
 15. The software of claim 13,wherein the message is sent individually to all the second enterprisesof the group in a point-to-point manner.
 16. The software of claim 13,wherein the event comprises the arrival at a first enterprise of abusiness document.
 17. The software of claim 13, wherein the workflowcomprises an automated system-to-system workflow.
 18. The software ofclaim 13, wherein the workflow comprises a user-interface workflow. 19.A system for multi-enterprise workflow communication, comprising: meansfor executing at least a portion of a workflow at a first enterprise;means for, in response to execution of the at least a portion of theworkflow at the first enterprise, triggering a workflow manager at thefirst enterprise operable to manage operations associated with theworkflow and to access an event manager at the first enterprise on anoccurrence of a predefined event in the workflow; and means for, basedon that occurrence of the event and according to a first underlyingparameterized workflow, communicating a plurality of messages from theevent manager at the first enterprise to a particular group of aplurality of second enterprises with which the first enterprisecollaborates to notify the second enterprises in the particular group ofthat occurrence of the event: the first underlying parameterizedworkflow requiring for its operation parameterized data sufficient toparticularize the first underlying parameterized workflow, eachparticularization of the first underlying parameterized workflowaccording to associated parameterized data comprising a separateinstance of the first underlying parameterized workflow; the particulargroup of second enterprises being one of a plurality of groups of secondenterprises, the first underlying parameterized workflow beingparticular to the particular group of second enterprises; the messagesbeing communicated substantially simultaneously to the secondenterprises in the particular group; each message being communicated toa corresponding one of the second enterprises in the particular groupaccording to a corresponding instance of the first underlyingparameterized workflow, the corresponding instance being particular tothe corresponding one of the second enterprises in the particular group;each message containing parameterized data specific to that occurrenceof the event and also specific to the corresponding one of the secondenterprises in the particular group, the parameterized data in themessage sufficient to particularize the first underlying parameterizedworkflow to yield the corresponding instance; each message beingcommunicated to the corresponding one of the second enterprises in theparticular group across an enterprise boundary of the first enterpriseand across an enterprise boundary of the corresponding one of the secondenterprises in the particular group; and means for, based on thatoccurrence of the event and according to a second underlyingparameterized workflow different from the first underlying parameterizedworkflow, initiating an instance of the second underlying parameterizedworkflow.